Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/middlewares/bot-membership-handler.ts`:
- Around line 55-60: The current flow returns immediately when redisCheck is
truthy and writes a permanent entry via this.TEMP_redis.write after a successful
backend query (api.tg.groups.getById.query), which can permanently skip future
reconciliation; update the TEMP cache usage so writes include an expiration
(TTL) and/or add an existence verification step: when calling
this.TEMP_redis.write(ctx.chat.id.toString(), ctx.chat.id) use the cache
client's TTL-aware API (or wrap writes to store an expiry) and ensure the
redisCheck path validates age/expiry (or performs a lightweight recheck) before
returning next(), and add explicit invalidation hooks where backend removals
occur so stale keys are removed.
- Line 57: The current call to api.tg.groups.getById.query is swallowing all
errors via .catch(() => null) which conflates transport/runtime failures with a
genuine "not found" and can incorrectly trigger GroupManagement.create; replace
the single-line .catch by explicitly distinguishing not-found (e.g., check for a
404/NotFound error from the API) from other errors: perform the call inside a
try/catch, return null only when the caught error indicates the group is absent,
and rethrow or propagate any other error so that backend failures are not
treated as "missing" (refer to the api.tg.groups.getById.query invocation and
the downstream GroupManagement.create usage to ensure the control flow is
corrected).